home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group98a.txt
/
000035_icon-group-sender _Wed Feb 11 12:25:57 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2000-09-20
|
3KB
Return-Path: <icon-group-sender>
Received: from kingfisher.CS.Arizona.EDU (kingfisher.CS.Arizona.EDU [192.12.69.239])
by baskerville.CS.Arizona.EDU (8.8.7/8.8.7) with SMTP id MAA07211
for <icon-group-addresses@baskerville.CS.Arizona.EDU>; Wed, 11 Feb 1998 12:25:57 -0700 (MST)
Received: by kingfisher.CS.Arizona.EDU (5.65v4.0/1.1.8.2/08Nov94-0446PM)
id AA21187; Wed, 11 Feb 1998 12:25:56 -0700
Message-Id: <34E1CDA3.2C40@gte.net>
Date: Wed, 11 Feb 1998 10:11:15 -0600
From: Mark Evans <evans@gte.net>
Reply-To: evans@gte.net
Organization: None
X-Mailer: Mozilla 3.01 (Win95; I)
Mime-Version: 1.0
To: icon-group@optima.CS.Arizona.EDU
Subject: Re: Stand-alone executables
References: <Pine.GSO.3.95.980211014253.12633A-100000@pandora>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
Content-Length: 1796
Ramon Pereda wrote:
>
> On Tue, 10 Feb 1998, Mark Evans wrote:
>
> > Under Windows/DOS, does there exist any method of bundling the "iconx"
> > interpreter with compiled icon code to create a true "stand-alone"
> > executable?
>
> No, there does not. [snip]
>
> Ideally one would like a platform independent way of attaching the input
> to the interpreter to the end executable and to inform the interpreter to
> start reading at the some point in its own executable. Perl2exe does this
> without recompiling perl.
>
> If anyone has some techniques, experience, or advice they would like
> to share on this, please speak up. I'd be glad to chase down any leads.
>
> -ray
I don't follow the reasoning of attaching the input data to the chain.
The whole point of writing programs is so that they can accept multiple
inputs over some period of time. If you compile your input into your
program, you cannot change it without recompiling.
As far as the stand-alone interpretive system goes, one method would be
to recompile the icon interpreter as (1) an object code library (static
linkage) or (2) a DLL (dynamic linkage). Then it becomes a fairly easy,
if tedious, matter to create stand-alone executables. You would not be
limited by the capabilities of the Icon runtime environment, for you
would be building your own from scratch.
The run-time image of an Icon program would be part of the stand-alone,
which would issue calls into the static or dynamic library.
I suppose that the static library is the more conservative approach and
probably the best one. I never did like the Windows design that forces
your system to depend on a single folder housing five thousand DLLs.
Like the proverbial string, you start pulling one out, and then the
whole building collapses.
Mark